home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20041116-20060924
/
000079_bonomi@host122.r-bonomi.com_Thu Mar 31 12:34:00 2005.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Path: newsmaster.cc.columbia.edu!newsfeed.nyu.edu!logbridge.uoregon.edu!canoe.uoregon.edu!newshub.sdsu.edu!tethys.csu.net!news-hog.berkeley.edu!newsfeed.berkeley.edu!ucberkeley!sn-xit-03!sn-xit-12!sn-xit-01!sn-post-01!supernews.com!corp.supernews.com!not-for-mail
From: bonomi@host122.r-bonomi.com (Robert Bonomi)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: DIAL-class command failed
Date: Thu, 31 Mar 2005 01:38:28 -0000
Organization: Widgets, Inc.
Message-ID: <114ml4ksaorrbaf@corp.supernews.com>
References: <1112180328.744431.319190@o13g2000cwo.googlegroups.com>
X-Newsreader: trn 4.0-test76 (Apr 2, 2001)
Originator: bonomi@host122.r-bonomi.com (Robert Bonomi)
X-Complaints-To: abuse@supernews.com
Lines: 54
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:15315
In article <1112180328.744431.319190@o13g2000cwo.googlegroups.com>,
vikrant.shahir@gmail.com <vikrant.shahir@gmail.com> wrote:
>hi
>
>computer 'A' and computer 'B' are connected to a GSM modem each.
>Both are linux machines(Redhat 9) and are using ckermit.
>Well i want to connect these computers so that i can transfer a file
>from computer 'A'
>to computer 'B'.
>
>to do this i kept computer 'B' in answer mode (using kermit) and then
>computer 'A' dials(using kermit) to that computer.
>
>Well it should work this way and get connected , so that i can transfer
>the file.
>
>But it doesn't work and ...the answering machine throws out an
>error(following)
>
>
>
>(/root/) C-Kermit>answer
> Waiting for phone call...
> Device: /dev/ttyS0, modem: generic, speed: 9600
> Answer timeout: (none)
> To cancel: type your interrupt character (normally Ctrl-C).
>+++
>ATQ0H0
>+ATQ0H0
>OK
> Modem hangup OK
> Initializing: 14:52:55...
>ATQ0V1
>ATQ0V1
>OK
>ATS0=1
>OK
>
>
>RING
>
>
>+CLIP: "+919821328531",145
>
*THERE* is the cause of the problem.
The modem is sending "Caller ID" information, which
the 'answer' script is *not* expecting.
Consult your modem manual, and find the appropriate command
to tell it _NOT_ to send caller ID info.
That should fix things.